Systems and methods for developing digital experience applications

ABSTRACT

In one implementation, systems and methods are provided for developing a computer-implemented digital experience application having a first and a second micro-application. Each micro-application includes a front end interface configured to receive and display information. The first micro-application includes a first event manager configured to detect an application event belonging to a category, and a first state manager configured to detect an application state belonging to the category. The digital experience application further includes a driver application configured to host the first and second micro-applications, an event hub configured to receive the detected application event from the first micro-application, and a state store configured to store the detected application state received from the first micro-application. The second micro-application includes a second event manager configured to receive the detected application event from the event hub, and a second state manager configured to receive the detected application state from the state store.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/010,074, filed on Sep. 2, 2020, which claims priority to U.S.Provisional Patent Application No. 62/983,529, filed on Feb. 28, 2020,the entire contents of which are incorporated herein by reference.

The present application incorporates by reference Provisional U.S.Patent Application Ser. No. 62/983,535, filed Feb. 28, 2020, andProvisional U.S. Application Ser. No. 62/983,581, filed Feb. 29, 2020.The patent applications cited herein are incorporated by reference intheir entireties, except for any definitions, subject matter disclaimersor disavowals, and except to the extent that the incorporated materialis inconsistent with the express disclosure herein, in which case thelanguage in this disclosure controls.

TECHNICAL FIELD

The present disclosure relates generally to computer-implemented systemsand methods for developing digital experience applications. Morespecifically, and without limitation, this disclosure relates tocomputer-implemented systems and methods for developing digitalapplications using one or more discrete micro-applications.

BACKGROUND

In digital application systems, it is often desirable to buildfunctionality in small, discrete pieces commonly referred to as“micro-applications” or “MicroApps.” Micro-applications allow digitalapplication developers to work independently from one another onseparate features and functions. They also allow developers to avoidre-writing code for the same tasks when developing new applications.Existing systems and methods for developing micro-applications, however,suffer from a number of drawbacks. For example, existing systems andmethods are unable to standardize the communication pattern betweenmicro-applications. This requires developers to write specific code,often for two or more micro-applications, so that the micro-applicationscan share information. In addition, existing systems and methods areinefficient because micro-applications are coupled through dependencies,resulting in micro-applications that are not self-reliant but ratherrely on functions and outputs from other applications ormicro-applications. Furthermore, existing systems and methods arecumbersome to use by developers, leading to degradation of code quality.

Accordingly, there is a need to overcome these and other drawbacks ofexisting systems and for improved systems and methods for developingdigital experience applications.

SUMMARY

In view of the foregoing, embodiments of the present disclosure addressdisadvantages of existing systems by providing novelcomputer-implemented systems, methods, and techniques for developingdigital experience applications.

Embodiments of the present disclosure provide a computer-implementeddigital experience application may be developed. The digital experienceapplication may include a driver application that may be configured tohost a plurality of micro-applications. The digital experienceapplication may include a first micro-application and a secondmicro-application. Each micro-application may include a front endinterface configured to receive and display information. The firstmicro-application may include an event manager configured to detect anapplication event belonging to a category. The first micro-applicationmay further include a state manager configured to detect an applicationstate belonging to the category. The digital experience application mayinclude a driver application configured to host the first and secondmicro-applications. Digital experience application may include an eventhub configured to receive the detected application event from the firstmicro-application and a state store configured to receive the detectedapplication state from the first micro-application and store thedetected application state. The second micro-application may include anevent manager configured to receive the detected application event fromthe event hub, and a state manager configured to receive the detectedapplication state from the state store.

According to embodiments of the present disclosure, the event hub may beconfigured to receive the detected application event in response to auser interaction with the front end interface of the firstmicro-application.

According to embodiments of the present disclosure, the state store maybe configured to receive the detected application state in response to auser interaction with the front end interface of the firstmicro-application.

According to embodiments of the present disclosure, the secondmicro-application may be subscribed to receive an application eventbelonging to the category, and the event hub may be configured totransmit the detected application event to the second micro-applicationevent manager based on the subscription.

According to embodiments of the present disclosure, the secondmicro-application may be subscribed to receive an application statebelonging to the category, and the state store may be configured totransmit the detected application state to the second micro-applicationstate manager based on the subscription.

According to embodiments of the present disclosure, the detectedapplication event may include a source identifier identifying the firstmicro-application. The second micro-application may be subscribed toreceive an application event transmitted from the firstmicro-application, and the second micro-application event manager may beconfigured to receive the detected application event from the event hubbased on the source identifier.

According to embodiments of the present disclosure, the detectedapplication state may include a source identifier identifying the firstmicro-application. The second micro-application may be subscribed toreceive an application state transmitted from first micro-application,and the second micro-application event manager may be configured toreceive the detected application event from the state store based on thesource identifier.

According to embodiments of the present disclosure, driver applicationmay comprise an event listener configured to listen for an applicationevent belonging to the category. The event listener may be configured toreceive the detected event from the event hub, and the secondmicro-application event manager may be configured to receive thedetected application event from the event hub via the event listener.

According to embodiments of the present disclosure, the driverapplication may be configured to load, in response to the event listenerreceiving the detected event, a third micro-application. The thirdmicro-application may comprise a third micro-application state managerconfigured to receive the detected application state from the statestore.

According to embodiments of the present disclosure, the digitalexperience application comprises a single page application.

According to embodiments of the present disclosure, the digitalexperience application may comprise a page component configured toposition the first micro-application at a first position within theapplication and position the second micro-application at a secondposition within the application.

According to embodiments of the present disclosure, the digitalexperience application may comprise an error handler configured todetect an error condition in at least one of first micro-application andsecond micro-application.

According to embodiments of the present disclosure, the firstmicro-application may comprise an outer interface configured to exchangeinformation with a source of information.

According to embodiments of the present disclosure, the firstmicro-application may comprise a front end interface and an outerinterface that are deployed as a separate docker container.

Embodiments of the present disclosure provide a computer-implementedmethod for providing a digital experience. The method may compriseoperations performed by at least one processor. The operations maycomprise detecting, at an event manager of a first micro-application, anapplication event belonging to a category. The method may comprisedetecting, at a state manager of the first micro-application, anapplication state belonging to the category. The method may comprisereceiving, at an event hub, the detected application event from theevent manager of the first micro-application. The method may comprisereceiving, at a state store, the detected application state from thestate manager of the first micro-application. The method may comprisestoring, at the state store, the detected application state. The methodmay comprise receiving, at an event manager of a secondmicro-application, the detected application event from the event hub.The method may comprise receiving, at a state manager of the secondmicro-application, the detected application state from the state store.

According to embodiments of the present disclosure, thecomputer-implemented method for providing a digital experience mayfurther comprise determining whether the second micro-application issubscribed to receive an application event belonging to the category andtransmitting, based on the determination, the detected application eventto the second micro-application event manager.

According to embodiments of the present disclosure, thecomputer-implemented method for providing a digital experience mayfurther comprise determining whether the second micro-application issubscribed to receive an application state belonging to the category,and transmitting, based on the determination, the detected applicationstate to the second micro-application state manager.

According to embodiments of the present disclosure, thecomputer-implemented method for providing a digital experience mayfurther comprise determining whether the second micro-application issubscribed to receive an application state belonging to the category,and transmitting, based on the determination, the detected applicationstate to the second micro-application state manager.

Embodiments of the present disclosure provide a tangible, non-transitorycomputer-readable memory device that stores a set of instructions. Theset of instructions, when executed by at least one processor, cause theat least one processor to perform operations. The operations maycomprise detecting, at an event manager of a first micro-application, anapplication event belonging to a category. The operations may comprisedetecting, at a state manager of the first micro-application, anapplication state belonging to the category. The operations may comprisereceiving, at an event hub, the detected application event from theevent manager of the first micro-application. The operations maycomprise receiving, at a state store, the detected application statefrom the state manager of the first micro-application. The operationsmay comprise storing, at the state store, the detected applicationstate. The operations may comprise receiving, at an event manager of asecond micro-application, the detected application event from the eventhub. The operations may comprise receiving, at a state manager of thesecond micro-application, the detected application state from the statestore.

The systems and methods disclosed herein may be used in variousapplications and vision systems, such as business systems and systemsthat benefit from building functionality using small, discrete pieces.

It is to be understood that the foregoing general description and thefollowing detailed description are exemplary and explanatory only, andare not restrictive of the disclosed embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate disclosed embodiments and,together with the description, serve to explain the disclosedembodiments. In the drawings:

FIG. 1 is a schematic representation of an exemplarycomputer-implemented digital experience application comprising aplurality of micro-applications, according to embodiments of the presentdisclosure.

FIG. 2 is a schematic representation of an exemplary driver applicationhosting a collection of micro-applications according to embodiments ofthe present disclosure.

FIG. 3 is a schematic representation of an exemplary digital experienceapplication according to embodiments of the present disclosure.

FIG. 4 is a schematic representation of an exemplarycomputer-implemented event hub for routing event information of adigital experience application, according to embodiments of the presentdisclosure.

FIG. 5 is a schematic representation of an exemplary embodimentdepicting an event hub enabling communication between micro-applicationsto share event information according to embodiments of the presentdisclosure.

FIG. 6 is a schematic representation of an exemplary digital experienceapplication enabling micro-applications to share information accordingto embodiments of the present disclosure.

FIG. 7 is a schematic representation of an exemplarycomputer-implemented state store for storing state information of adigital experience application 700, according to embodiments of thepresent disclosure.

FIG. 8 is a schematic representation of an exemplary method fordynamically loading a micro-application according to embodiments of thepresent disclosure.

FIG. 9 is a schematic representation of an exemplary method fornavigating between page components.

FIG. 10 is a schematic representation of a computer-implemented systemfor developing digital experience applications according to embodimentsof the present disclosure.

FIG. 11 is a schematic representation of an exemplary command lineinterface according to embodiments of the present disclosure.

FIG. 12 is an exemplary method of creating a micro-application using adeveloper utility according to embodiments of the present disclosure.

FIG. 13 is a schematic representation of an exemplarycomputer-implemented developer utility for developing digital experienceapplications according to embodiments of the present disclosure.

FIG. 14 is an exemplary developer utility according to embodiments ofthe present disclosure.

FIG. 15 is a flowchart of an exemplary computer-implemented method forproviding a digital experience through an application in accordance withsome embodiments.

DETAILED DESCRIPTION

Reference will now be made in detail to exemplary embodiments, discussedwith regards to the accompanying drawings. In some instances, the samereference numbers will be used throughout the drawings and the followingdescription to refer to the same or like parts. Unless otherwisedefined, technical and/or scientific terms have the meaning commonlyunderstood by one of ordinary skill in the art. The disclosedembodiments are described in sufficient detail to enable those skilledin the art to practice the disclosed embodiments. It is to be understoodthat other embodiments may be utilized and that changes may be madewithout departing from the scope of the disclosed embodiments. Forexample, unless otherwise indicated, method steps disclosed in thefigures can be rearranged, combined, or divided without departing fromthe envisioned embodiments. Similarly, additional steps may be added orsteps may be removed without departing from the envisioned embodiments.Thus, the materials, methods, and examples are illustrative only and arenot intended to be necessarily limiting.

Disclosed embodiments provide a standardized communication patternbetween micro-applications that is not dependent on the environment.Disclosed embodiments use application states, rather than dependencies,to create micro-applications that are loosely coupled, resulting inmicro-applications that can be more easily integrated into new systems.Disclosed embodiments provide a simple and elegant set of utilities thatare integrated into the development process to help developers maintainhigh code quality and adhere to the same development techniques.

Digital Experience Application Comprising a Collection ofMicro-Applications

FIG. 1 is a schematic representation of an exemplarycomputer-implemented digital experience application 100. In accordancewith disclosed embodiments, digital experience application 100 maycomprise a plurality of micro-applications 106 configured to detectevents relating to the application 100 (i.e., application events) andstates relating to the application 100 (i.e., application states). Thedigital experience application 100 may include one or more driverapplications 102 for hosting and managing the plurality ofmicro-applications 106. A driver application 102, also referred to as a“channel application,” can include one or more page components 104configured to lay out and route information to and from the plurality ofmicro-applications 106. The driver application 102 may also include oneor more event hubs 130 configured to receive the detected applicationevents from the plurality of micro-applications 106 and route thedetected application events to the plurality of micro-applications 106and/or other components of application 100. Driver application 102 mayalso include one or more state stores 128 configured to store thedetected application states received from the plurality ofmicro-applications.

In some embodiment, the digital experience application 100 may compriseone or more event listeners 120 configured to respond when an eventoccurs in the plurality of micro-applications 106; one or more errorhandlers 122 configured to respond to error conditions in the pluralityof micro-applications 106; one or more routers 124 configured to forwardinformation received from the plurality of micro-applications 106; andone or more common libraries 126 comprising resources and/or functionsused by the plurality of micro-applications 106. In various embodiments,the driver application 102 can be configured to provide information tothe page component 104 for ensuring that the plurality ofmicro-applications 106 function and are displayed in a similar manner.For example, the driver application 102 can provide, to the pagecomponent 104, information corresponding to a common style scheme, whichmay include information relating to font styles, font size, buttons,links, and the like. In some embodiments, the information may relate tofeatures for backwards compatibility, for example to provide backwardscompatibility with older web browsers for displaying the application100. This may include polyfill code or the like to allow developers touse an interface or feature of application 100 whether it is supportedby a browser or not.

A page component 104 may include router configuration information 134 sothat page component 104 may be configured to represent or act as a routein the driver application 102 and host a micro-application 106corresponding to that route. For example, if a user interacts with amicro-application 106, the page component 104 may be configured to senddata corresponding to that user interaction to the driver application102. As another example, a user may interact with a micro-application ona first page component which may act as a route to send datacorresponding to that user interaction to a second page component(enabling page routing). A page component 104 may include layout 132providing information configured to specify the layout of themicro-application 106. To illustrate using FIG. 1 as an example, layout132 may include information such that page component 104 may beconfigured to position a first micro-application 106 at the top of thepage component 104, corresponding to a navigation bar micro-application108 in this example (e.g., a micro-application configured to navigatefrom the page component as shown in FIG. 3 ); position a secondmicro-application, corresponding to a header micro-application 110 inthis example, below the first micro-application 108 (e.g., a headermicro-application containing a welcome banner as shown in FIG. 3 );position a third micro-application, corresponding to a footermicro-application 118 in this example, at the bottom of the pagecomponent 104 (e.g., a footer micro-application containing data of abusiness or copyright information as shown in FIG. 3 ); and positionfourth, fifth, and sixth micro-applications (112, 114, 116) between theheader micro-application 110 and footer micro-application 118 (e.g., adeposit account summary micro-application for displaying to a user alldeposit accounts related to the user as shown in FIG. 3 ).

In some embodiments, driver application 102 aggregates a plurality ofmicro-applications 106 to develop the user experience of the application100. This framework enables application developers to buildapplications, such as application 100, using small, discrete pieces(i.e., the micro-applications). In some embodiments, the driverapplication 102 comprises a Single Page Application (SPA), which may bedeveloped, for example, using the Angular platform. A micro-application106 can be configured to perform one or more discrete functions, forexample using functional logic. The micro-application 106 may representan independent vertical slice of the business functionality provided bythe application 100. The micro-application 106 can comprise a front-end136, (i.e. a user interface, such as a graphical user interface or“GUI”) configured to interface with a user by receiving inputinformation from the user and/or providing information to the user. Forexample, a micro-application 106 may contain a front-end 136 forreceiving user input in the form of a mouse-click on a browser,interaction with a button, touch screen, touch panel, keyboard input, orthe like. Front end 136 may also provide information to the user througha display or the like. The front-end 136 of the micro-application 106may be created using a front-end web platform for building mobile anddesktop web applications, such as the Angular platform. In someembodiments, as shown in FIG. 1 , micro-application 106 may be loadedonto the page component 104 and to the driver application 102 using aweb platform such as HTML5 web component technology or the like.

In some embodiments, the micro-application 106 may comprise an outerinterface 138 (also referred to as a back end) corresponding to thefront end 136 of the micro-application 106. The outer interface 138 maybe configured for receiving information from and sending information toa component or source outside the driver application 102. For example,the outer interface 138 may be configured for receiving information froma database. In some embodiments, the outer interface 138 may be anapplication programming interface (API). The outer interface 138 mayroute information to and from an Inner API, as disclosed in ProvisionalU.S. Patent Application Ser. No. 62/983,535, the contents of which areincorporated herein. The micro-application 106 may contain an outerinterface 138 developed using spring boot or Bootstrap framework. Insome embodiments, the front-end 136 and the outer interface 138 of amicro-application 106 may be deployed as a separate container, such as adocker container, in a container application, such as OpenShiftContainer Platform (OCP), or the like. This enables themicro-application 106 to run quickly and reliably from one computingenvironment to another.

In some embodiments, the micro-application 106 can further comprise anevent manager 140 configured to send and receive event information. Forexample, event manager 140 may be configured to detect an applicationevent belonging to a category and transmitting the detected applicationevent. The detected application event may be transmitted to event hub130, for example. The micro-application 106 can further comprise a statemanager 142 configured to send and receive state information. Forexample, state manager 142 may be configured to detect an applicationstate belonging to a category and transmitting the detected applicationstate. The detected application event may be transmitted to state store128, for example, for storage. In some embodiments, themicro-application can further comprise a debug drawer 144 configured tocapture and replay events as a part of the micro-applicationcommunication.

In some embodiments, a micro-application 106 may not include an outerinterface 138. Here, a micro-application 106 without an outer interface138 may be configured to listen for events and state changes from othermicro-applications. For example, a first micro-application may sendevent information to event hub 130 and state information to state store128. A second micro-application configured to listen for events andstate changes from first micro-application, or alternatively, the eventsand state changes belonging to a specific category, may then receive theevent information from event hub 130 and state information from statestore 128.

Event hub 130 can be configured to route event information to and fromthe plurality of micro-applications 106 and/or the driver application102. The plurality of micro-applications 106 and/or the driverapplication 102 can be configured to transmit or receive eventinformation to and/or from the event hub 130 as a result of or inresponse to a user input or other user interaction withmicro-applications 106. Alternatively or additionally, the plurality ofmicro-applications 106 and/or the driver application 102 may beconfigured to transmit or receive event information to and/or from theevent hub 130 as a background process. Accordingly, micro-applications106 and/or the driver application 102 may publish events in response toeither a user interaction or a background process. In some embodiments,event hub 130 may be integrated into the driver application 102. Theevent hub 130 may be configured to route information based on one ormore criteria. For example, the event hub 130 may be configured to routeevent information from a first source to a first set ofmicro-applications, and it may be configured to route event informationfrom a second source to a second set of micro-applications. The eventhub 130 may route or filter the event information from the first andsecond sources using a source identification value emitted by thesource.

In some embodiments, micro-applications 106 and/or driver application102 may “subscribe” to receiving event information. For example,micro-applications 106 and/or driver application 102 may be subscribedto receiving event information from a specific source. In this case, theevent hub 130 may be configured to route event information only tomicro-applications 106 or driver application 102 subscribed to receivinginformation from the specific source before the event occurs. In someembodiments, a micro-application 106 or driver application 102 may belate in subscribing to receive the event information from the sourcebefore the event occurs. In this case, the micro-application 106 ordriver application 102 that subscribes late does not receive the eventinformation. In some embodiments, the event hub 130 may be configured toroute “special” event information differently, such as for navigatingthe driver application 102 to a different page, as described in furtherdetail below. In some embodiments, the event hub 130 can be configuredto be a singleton, such that only a single instance of the eventinformation is relayed. In this manner, the system can ensure that onlycorrect and up-to-date event information is transmitted.

In some embodiments, state store 128 may be integrated into the driverapplication 102. State store 128 can be configured to store stateinformation relating to application 100. The state store 128 maycomprise a database, server, local storage, or the like. For example,state store 128 may comprise in-browser memory, with state informationbeing stored as an object, such as a JavaScript Object Notation (JSON)object. The state store 128 can be further configured to route stateinformation to and/or from the plurality of micro-applications 106and/or the driver application 102. The plurality of micro-applications106 and/or the driver application 102 can be configured to transmit orreceive state information to and/or from the state store 128 as a resultof or in response to a user input or other user interaction withmicro-applications 106. Alternatively or additionally, the plurality ofmicro-applications 106 and/or the driver application 102 may beconfigured to transmit or receive state information to and/or from thestate store 128 as a background process. Accordingly, micro-applications106 and/or driver application 102 may update the application state ofapplication 100.

In some embodiments, similar to the event hub 130 described above, statestore 128 can be further configured to route state information based onone or more criteria. For example, the state store 128 may be configuredto route state information from a first source to a first set ofmicro-applications, and may route state information from a second sourceto a second set of micro-applications. The state store 128 may route thestate information from the first and second sources using a sourceidentification value emitted by the source. In some embodiments,micro-applications 106 and/or driver application 102 may “subscribe” toreceiving state information. For example, micro-applications 106 and/ordriver application 102 may be subscribed to receiving state informationfrom a specific source. In this case, the state store 128 may beconfigured to send state information only to micro-applications 106 ordriver application 102 subscribed to receiving state information fromthe specific source before the state changes. In some embodiments, amicro-application 106 or driver application 102 may be late insubscribing to receive the state information from the source. In thiscase, the micro-application 106 or driver application 102 thatsubscribes late does not receive the state information. In someembodiments, the state store 128 can be configured to be a singleton,such that only a single instance of the state information is relayed. Inthis manner, the system can ensure that only correct and up-to-datestate information is transmitted, as the state store 128 acts as thesingle source of truth. In various embodiments, the state store 128 canbe configured to automatically transmit state information to newmicro-applications 106 that are added to the driver application 102and/or the digital experience application 100.

Driver Application for Hosting Micro-Applications

FIG. 2 is a schematic representation of an exemplary driver applicationhosting a collection of micro-applications according to embodiments ofthe present disclosure. The driver application may be a Single PageApplication (SPA) 200, which may be developed, for example, using theAngular platform. SPA may be configured to load a single HTML page anddynamically update that page as the user interacts with the application.SPA 200 includes a page component 202 and hosts micro-applications 204,206, 208, and 210 to create the user experience of the SPA 200.Micro-application 208 may include a front end 212 configured tointerface with a user by receiving input information from the userand/or providing information to the user. Micro-application 208 mayfurther include an outer interface 214 such as an API. Outer API 214 maybe configured to interact with components outside of SPA 200, such as aSystems of Record (SOR) 218 via Write Inner API 216, and/or interactwith a Book of Reference 222 via Read Inner API 220.

Page Component providing Layout and Configuration for Micro-Application

FIG. 3 is a schematic representation of an exemplary digital experienceapplication in accordance with some embodiments. Digital experienceapplication 300 may provide a user with a digital experience relating toan application, such as, for example, a financial application foraccessing a bank account. For example, a user may interface with digitalexperience application 300 using a computer, mobile device (e.g.,cellular phone, smartphone, tablet, personal digital assistant, etc.),or other electronic device to review and/or interact with a bankaccount. Application 300 may include a driver application 302, one ormore page components (304, 306, 308), and one or more micro-applications(310, 312, 314, 316, 318, 320, 322, 324, 326). Driver application 302may be configured to host and manage the micro-applications relating tothe bank account of a user, such as “Sarah” as illustrated in FIG. 3 .Page components 304, 306, and 308 may each include layout and routerconfiguration information, as described above with respect to layout 132and router configuration information 134, configured to lay out androute information to and from the plurality of micro-applications310-326. Micro-applications 310-326 may be loaded onto page components304, 306, and 308 according to layout information in the layout of eachpage component, as described above.

For example, page component 304 may be configured to position amicro-application, navigation bar micro-application 310, at the top ofpage component 304. Navigation bar micro-application 310 may beconfigured to create the page header for application 300 and enablenavigation from the page component 304 to other applications or pagecomponents. For example, navigation bar micro-application 310 may enablenavigation to other page components associated with “accounts,”“transfer,” “paybills,” “rewards,” or “help.” Page component 304 may beconfigured to position a micro-application, header micro-application312, below navigation bar micro-application 310. Headermicro-application 312 may be configured to create a personalized welcomebanner for an authenticated user, for example, displaying “WelcomeSarah,” as illustrated in FIG. 3 . Driver application 302 may includeanother page component 308 configured to position a micro-application,footer micro-application 326, at the bottom of page component 308.Footer micro-application 326 may be configured to provide business andcopyright information to the user. For example, footer micro-application326 may provide bank information relating to customer service hours,contact information, service agreements, privacy policies, and othersuch information.

Driver application 302 may further include page component 306 configuredto position one or more micro-applications between the headermicro-application 312 and the footer micro-application 326. For example,page component 306 may be configured to position micro-applications 314,316, 318 and 320 in a first vertical row on the left hand side of pagecomponent 306, and position micro-applications 322 and 324 in a secondvertical row on the right hand side of page component 306.Micro-applications 314, 316, 318 may be configured for providing adeposit account summary to create a summary and individualized view ofall deposit accounts (e.g., interest checking and virtual wallet)related to a user and/or any associated users, such as associated usersof a joint bank account. Micro-application 320 may be configured toprovide credit card account summary to create a summary andindividualized view of all Credit Card accounts related to the userand/or any associated users. Micro-applications 322 and 324 may beconfigured for providing tools and tips to the user to presentsuggestions for bettering the user experience.

The collection of micro-applications 310-326 in application 300 maytransmit and receive event information and state information to and froman event hub and a state store, similar to event hub 130 and state store128 described in FIG. 1 . For example, if the user makes a financialtransaction, such as a deposit into their checking account,micro-application 316 may detect event information relating to thedeposit and detect an update to the state of checking account. Thedetected event information and updated state may be received by eventhub 130 and state store 128, respectively. Additionally, an eventlistener may be configured to listen for events and state changes frommicro-application 316. In response to the detected event information andupdated state, event listener may enable the detected event informationand updated state to be transmitted from event hub 130 and state store128 to micro-application 314, for example, to update the total balanceinformation. Here, micro-application 314 may be subscribed to receiveevent and state information relating to a category, such as depositaccount information. Alternatively, micro-application 314 may besubscribed to receive event and state information from a source, such asmicro-application 316. In this and other ways, developers may buildmicro-applications to provide a user experience when accessingapplication 300.

Event Hub for Routing Event Information

FIG. 4 is a schematic representation of an exemplarycomputer-implemented event hub for routing event information of adigital experience application, according to embodiments of the presentdisclosure. Digital experience application 400 may include a driverapplication 402. Driver application 402 may integrate event hub 404 andhost a collection of micro-applications, such as micro-applications 414,416, 418, and 420. The functional behavior of the micro-applications414, 416, 418, and 420 may be governed by events, with eachmicro-application acting as an independent functional unit. In someembodiments, event hub 404 may be configured as a singleton instancesuch that only a single instance of the event information is relayed.This enables coordinated actions across the system with event hub 404serving as a communication hub that enables micro-applications 414, 416,418, 420 and driver application 402 to publish events. Event hub 404 maybe configured to receive event information from one or moremicro-applications 414, 416, 418, and 420 and then route the receivedevent information to one or more micro-applications 414, 416, 418, and420 or other components or micro-applications. The event hub 404 may beconfigured to route event information based on one or more criteria. Forexample, the criteria may relate to subscriptions, a category ofinformation, or a source of information.

As depicted in FIG. 4 , a first micro-application 414 may raise an eventat 406, for example, in response to a user interaction or backgroundprocess. Micro-application 414 may transmit event information for theraised event to the event hub 404. The event information may belong to acategory. For example, the event information may belong to a categoryrelating to balances for deposit accounts. Event hub 404 may beconfigured to determine where to route the event information receivedfrom micro-application 414. For example, event hub 404 may be configuredto determine if one or more micro-applications have subscribed toreceive events. For example, event hub 404 may determine thatmicro-application 416 is subscribed to receive events belonging to thecategory of event information received from micro-application 414. Forexample, event hub 404 may consult a data storage component, such as alookup table or other memory structure, to determine whethersubscriptions exist. Alternatively or additionally, event hub 404 maydetermine that micro-application 416 is subscribed to receive eventsraised from a particular source, such as micro-application 414. At 408,event hub 404 determines that micro-application 416 is subscribed toreceive events, for example, belonging to a category relating tobalances for deposit accounts. In response, event hub 404 routes theevent information received from micro-application 414 tomicro-application 416. In some instances, event hub 404 may route theevent information based on a source identification value emitted bymicro-application 414. For example, event hub 404 may determine thatmicro-application 416 is subscribed to events raised bymicro-application 414. Here, event hub 404 routes the event informationto micro-application 416 using the source identification value emittedby micro-application 414.

In some instances, a micro-application may not be subscribed to receiveevents. For example, micro-application 420 is not subscribed to receiveevents and will not, at 408, receive events from event hub 404. In someinstances, a micro-application 418 may have subscribed late, forexample, after the event has already been raised by micro-application414, and may not receive events, at 410, from event hub 404. In someembodiments, a driver application, such as driver application 402, maybe subscribed to receive event information from a micro-application inthe same manner as subscribed micro-application 416, as described above.In this instance, event hub 404 determines that driver application 402is subscribed to receive event information from micro-application 414,and transmits the event information received to driver application 402.

Micro-applications may publish events in response to a user interactionor a background process. For example, FIG. 5 is a schematicrepresentation of an exemplary embodiment depicting an event hubenabling communication between micro-applications to share eventinformation. Application 500 may include a driver application comprisinga page component 502 that may host gray micro-application 508 and redmicro-application 516. The driver application may also include an eventhub 504 and state store 506. Gray micro-application 508 may include afront end interface depicting three buttons: red button 510, blue button512, and purple button 514. At step 518, gray micro-application 508 maytrigger or detect an event (i.e. “red” event) as a result of a userinteraction with red button 510. Gray micro-application 508 may transmitevent information (containing a value) relating to the interaction withred button 510 (i.e., “red” event information) to event hub 504. Eventhub 504 may be configured to route event information based on one ormore criteria, as described above. Event hub 504 may determine that redmicro-application 516, at step 520, is subscribed to listen for eventinformation belonging to a category, such as red events. Event hub 504may then route the red event information to red micro-application 516based on the determination. In this way, a subscribing micro-applicationmay receive event information originating from gray micro-application508.

FIG. 6 is a schematic representation of an exemplary digital experienceapplication enabling micro-applications to share information accordingto embodiments of the present disclosure. Digital experience application600 may provide a user with a digital experience relating to anapplication, such as, for example, a financial application for accessinga bank account. Application 600 may include a driver application 602configured to host and manage the micro-applications relating to theuser's bank account. The micro-applications may individually satisfydifferent business functions relating to the user's bank account. Forexample, driver application 602 may host micro-application 616configured to provide a deposit account total balance; micro-application612 configured to provide deposit account summary information;micro-application 614 configured to provide virtual wallet accountsummary information; and micro-application 616 configured to providecredit card account summary. The collection of micro-applications 610,612, 614, 616 may be configured to share information to ensure aconsistent experience is delivered throughout application 600. Forexample, micro-applications 610, 612, 614, 616 may transmit and receiveevent information and state information to and from an event store andstate store, as described above. As depicted in FIG. 6 , individualaccount balance data may be shared (at steps 604, 606, 608) betweenmicro-applications 610, 612, 614, and 616 to present a summary balanceof all deposit accounts or all credit accounts.

State Store for Updating and Storing Application States

FIG. 7 is a schematic representation of an exemplarycomputer-implemented state store for storing state information of adigital experience application 700, according to embodiments of thepresent disclosure. Driver application 710 may include a firstmicro-application 712, a second micro-application 714, and a state store716. The state store 716 may be configured to route state informationbased on one or more criteria. For example, the criteria may relate tosubscriptions, a category of information, or a source of information. Asdepicted in FIG. 7 , micro-application 712 may send state information atstep 718 to the state store 716. The state information may be sent as aresult of a user interaction or background processes. The stateinformation may belong to a category. For example, the state informationmay belong to a category relating to account deposits. At step 718,micro-application 712 may update the state belonging to the depositcategory and send the updated state information to state store 716 forstorage. State store 716 may comprise a database, server, local storage,in-browser memory, or other memory structures for storing stateinformation.

In a similar fashion as with event hub, the state store 716 may beconfigured to send the state information to micro-applications that havesubscribed to indicate they wish to receive state information belongingto a specific category. State store 716 may determine thatmicro-application 714 is subscribed to listen to state information, suchas state changes, belonging to the deposit category. For example, statestore 716 may consult a data storage component, such as a lookup tableor other memory structure, to determine whether subscriptions exist.Alternatively or additionally, state store 716 may determine thatmicro-application 714 is subscribed to receive state changes transmittedfrom a particular source, such as micro-application 712. State store 716then routes the state information received from micro-application 712 tomicro-application 714. In some instances, state store 716 may route thestate information based on a source identification value emitted bymicro-application 712. For example, state store 716 may determine thatmicro-application 712 is subscribed to state changes provided bymicro-application 712. Here, state store 716 routes the stateinformation to micro-application 714 using the source identificationvalue emitted by micro-application 712.

Dynamic Loading of Micro-Applications

FIG. 8 is a schematic representation of an exemplary method fordynamically loading a micro-application, according to embodiments of thepresent disclosure. Here, an event hub and state store may enablecommunication with a first micro-application to dynamically load asecond micro-application. Application 800 may include a driverapplication hosting gray micro-application 810 and bluemicro-application 818 within a page component 802. In some embodiments,driver application may load gray micro-application 810 such that it isaccessible within application 800, without loading bluemicro-application 818. Driver application may also include an event hub804, state store 806, and event listener 808. Gray micro-application 810may include a front end interface depicting three buttons: red button812, blue button 814, and purple button 816.

As an exemplary first step 820, gray micro-application 810 may triggeror detect a state change belonging to a category, for example a “blue”category. The state change may be triggered or detected as a result of auser interaction with blue button 814 or alternatively, as a result of abackground process related to blue button 814. Gray micro-application810 may transmit state information (containing a value) relating to theinteraction with blue button 814 (i.e., “blue” state information) tostate store 806. State store 806 may be configured to store the bluestate information and/or update previously stored blue stateinformation. At step 822, gray micro-application 810 may trigger ordetect an event associated with the state change (i.e. a “blue” event)as a result of the user interaction with blue button 814. Graymicro-application 810 may transmit event information, containing a value(i.e., “blue” event information) associated with the state change toevent hub 804. Event listener 808 may be configured to listen for eventsbelonging to a category, such as blue events. Event listener 808 may besubscribed to receiving event information belonging to the category ofblue events. Event hub 804 may determine that event listener 808 issubscribed to listen for event information belonging to a category ofblue events. At step 824, event hub 804 may then route the blue eventinformation to event listener 808 based on the determination.

Event listener 808 may be configured to respond or perform an actionbased on receiving the blue event information from event hub 804. Forexample, at step 826, event listener 808 may communicate with driverapplication to generate or load blue micro-application 818. Bluemicro-application 818 may be configured to listen to state changesbelonging to a category. At step 828, state store 806 may determine thatblue micro-application 818 is subscribed to listen for state informationbelonging to the blue category, such as blue state changes. State store806 may then route the stored blue state information to bluemicro-application 818. In this way, newly-loaded blue micro-application818 is updated with the latest blue state information.

Navigation Between Page Components

FIG. 9 is a schematic representation of an exemplary method fornavigating from one page component to another page component, consistentwith embodiments of the present disclosure. In some embodiments, pagecomponent may be responsible for handling navigation between pages. Insome embodiments, an application may include multiple page components,wherein some page components are visible to the user while other pagecomponents are not visible to the user. Here, the user may navigate fromone page component (for example, a visible page component) to anotherpage component that was previously hidden from view. As depicted in FIG.9 , application 900 may include a driver application comprising a firstpage component 902 including gray micro-application 914. Graymicro-application may include a front end interface depicting threebuttons: red button 916, blue button 918, and purple button 920. Pagecomponent 902 may also include router configuration information 910 sothat page component 902 may be configured to act as a route in thedriver application. Driver application may comprise a second pagecomponent 904 including purple micro-application 922 and bluemicro-application 924. Page component 904 may also include routerconfiguration information 912. Driver application may also comprise anevent hub 906 and state store 908.

Gray micro-application 914 may trigger or detect an event (e.g., a“purple” event) as a result of a user interaction with purple button 920or alternatively, as a result of a background process related to purplebutton 920. At step 926, gray micro-application 914 may transmit eventinformation, containing a value, relating to a category to event hub906. For example, gray micro-application 914 may transmit purple eventinformation relating to the interaction with purple button 920 to eventhub 906. In addition to purple event information, gray micro-application914 may transmit navigation information to event hub 906 relating to thepurple event. In some instances, the navigation information may beretrieved from router configuration information 910. Event hub 906 maybe configured to route event information based on one or more criteria,as described above. At step 928, event hub 906 may route purple eventinformation to a second page component 904 based on the navigationinformation. At step 930, page component 904 may receive purple eventinformation and transmit it to purple micro-application 922 based on thenavigation information. For example, purple micro-application 922 may besubscribed to receiving events belonging to the purple category orevents belonging to a source such as gray micro-application 914. In someinstances, router configuration information 912 may receive or store thenavigation information received.

At step 924, blue micro-application 924 within second page component 904may, as a result of the purple event information, receive stateinformation from state store 908. For example, blue micro-application924 may be subscribed to listen to state information belonging to a bluecategory (i.e. blue state information). As a result of the purple eventinformation received at purple micro-application 922, state store 908may be configured to transmit updated blue state information to bluemicro-application 924.

Developer Utility and Tool Kit

FIG. 10 is a schematic representation of a computer-implemented systemfor developing digital experience applications, according to embodimentsof the present disclosure. Framework 1000 provides developers with acommon user interface framework enabling development of consistent andstandard digital experience applications. Framework 1000 may providedevelopers with the toolkit, components, and libraries to ensure properautomated testing, debug and build patterns. For example, framework 1000ensures applications may be built to architecturally-approved standards.Framework 1000 provides benefits over prior frameworks, as the frameworkenables scaffolding based on conventions, code standardization,reinforces best practices and code quality through linting rules,provides an enhanced developer experience, enables a custom buildprocess to optimize a bundle size based on local or productiondeployment, and standardizes the communication pattern through the useof an event hub and a state store.

Framework 1000 may comprise a command line interface (CLI) 1002, a corelibrary 1004, developer tools 1006, support library 1008, build tools1010, lint tools 1012, telemetry 1014, and micro-application portal1016. CLI 1002 is a command line tool for managing development of anapplication. CLI 1002 may comprise commands for generating, installing,and updating features. An example of CLI 1002 is illustrated in FIG. 11.

FIG. 11 is a schematic representation of an exemplary command lineinterface, such as CLI 1002. CLI 1100 provides a developer-friendlyutility for enforcing consistency and standardization during thedevelopment process. The framework enables developers to visualize thedriver application and micro-application interactions. The frameworkprovides functions for creating a new application, for example, byproviding a developer the ability to perform the following functions:create a driver application, such as driver application 1102; create anew micro-application 1108 using the micro-ap[plication project 1106;build and serve the micro-application 1108; create a page component suchas page component 1104 within driver application 1102; and append thenew micro-application 1108 to the driver application 1102.

Returning to FIG. 10 , core library 1004 may comprise a library tocreate an event hub, a state store, an event listener, an error handler,and other components of a driver application. Developer tools 1006 maycomprise a mock driver to be used as a test container, a debug drawer tocapture and replay events as part of communications of amicro-application, accessibility tool integration, a pattern library, orthe like. Support library 1008 may comprise a library to provide easyaccess to life cycle methods of micro-applications, destroy and clean upmicro-applications after use, generate error templates, generate loadcursors, or the like. Support library 1008 may provide commonfunctionalities and best practices to be followed by a developer.Support library 1008 may also comprise a library to eager or lazy loadmicro-applications. For example, lazy loading is a process for speedingup application load time by splitting the application into multiplebundles and loading them on demand (i.e. at run time). In this way,dependencies may be lazy loaded on an as-needed basis rather thaneager-loaded, which requires the dependencies or components be loaded onlaunch.

Build tools 1010 may comprise tools to build a driver application,create a page component, create a micro application, append amicro-application to a page component, for example. Lint tools 1012 maycomprise tools enabling automatically integrating standard rules andbest practices for the programming language being used and otherprogramming information such as TSLint, Stylelint, Prettier, Husky, orthe like. Telemetry 1014 may comprise integration such as Adobeintegration. Micro-application portal 1016 may comprise amicro-application catalog, micro-application preview, health checkintegration, RBT support, or the like. In some embodiments, librariesmay be externalized so that they may be changed without impacting thedevelopment of micro-applications.

FIG. 12 is an exemplary method of creating a micro-application using adeveloper utility, according to embodiments of the present disclosure.The developer utility enables a developer to build, test, and deploy(i.e., insert) new micro-applications within a driver application.Method 1200 begins at step 1202. Step 1202 may include performing a“new” CLI command to insert a new micro-application into a digitalexperience application. For example, a new micro-application may beinserted into a mock driver application to develop the newmicro-application with context. Step 1204 may include performing a“build” command to compile code belonging to the micro-application. Thismay ensure that no errors exist between the new micro-application andthe digital experience application. Step 1206 may include performing an“append” command to append the micro-application to the digitalexperience application.

FIG. 13 is a schematic representation of an exemplarycomputer-implemented developer utility for developing digital experienceapplications, according to embodiments of the present disclosure. In oneembodiment, the developer utility 1302 may comprise a series offunctions to create, manage, and debug micro-applications, such as graymicro-application 1306 and red micro-application 1308. For example, adeveloper utility may comprise the commands and libraries mentionedabove in connection with FIG. 10 .

In another embodiment, the developer utility may comprise a userinterface. The user interface may comprise one or more fields fordisplaying generated micro-applications. A generated micro-application,such as gray micro-application 1306, may be configured to display anaction that may be configured to trigger an application event when adeveloper interacts with it, such as red action 1310, blue action 1312,green action 1314, and purple action 1316. A generated micro-applicationmay be further configured to display data received as a result of anapplication event, such as such as red micro-application 1308 displayingdata received 1320 as a result of red action 1310. The user interfacemay further comprise an error field 1322 that may be configured todisplay errors resulting from executing the application; an event fieldthat may be configured to display previous application events; a currentstate field 1318 that may be configured to display current stateinformation of the application; and an event changes field 1324 that maybe configured to display changes in the state of the application. It isto be understood that the user interface may contain more or less fieldsthan those indicated above.

In another embodiment, the developer utility may comprise one or moreutilities integrated into the application development process. Forexample, as described above, micro-applications may be configured tocontain a debug drawer to be able to capture and replay events as a partof the micro-application communication. Furthermore, the developerutility may comprise one or more of the following: automatic codeformatting to format code into a uniform format for a more elegant andeasy-to-read code; integrated linting techniques to automaticallyintegrate standard rules and best practices for the programming languagebeing used (e.g., TypeScript) and other programming information (e.g.,stylesheets); pre-committing hooks to automatically integrate standardrules and best practices before a developer shares his or her code(e.g., by pushing the code to a Bitbucket or GitHub repository); testintegration to automatically integrate testing units during the buildprocess to ensure that the application functions properly after new codeis added; a customizable build process to change the building processdepending on the needs (e.g., development vs. production deployment); amicro-application project configured to able to have a separate folderfor micro-application related components; and a root level componentconfigured to be used as a mock driver-application container.

FIG. 14 is an exemplary developer utility, according to embodiments ofthe present disclosure. A developer utility, such as a debugger 1400,may be configured to display event information and state informationbeing exchanged between micro-applications. This utility enablesvisualizing the interactions between states, events, andmicro-applications and their components, allowing a developer to quicklyvalidate micro-application functionality and behavior.

Debugger 1400 enables a developer to visualize an event hub 1404 withina driver application. In some embodiments, debugger 1400 enables thedeveloper to review how event hub 1404 interacts with micro-applications1414, 1416, 1418, and 1420. For example, debugger enables the developerto visualize the logical flow of steps. At 1406 micro-application 1414raises an event belonging to a category. Event information relating tothe event is sent to event hub 1404. At step 1408, a determination thatmicro-application 1416 is subscribed to receive events relating to thecategory (or alternatively relating to micro-application 1414) causesmicro-application 1416 to receive the raised event. At step 1410, adetermination that micro-application 1418 is subscribed to receiveevents relating to the category, but that the subscription occurredlate, causes micro-application 1418 to not receive the raised event. Atstep 1412, a determination that micro-application 1420 is not subscribedto receive events belonging to the category causes micro-application1420 to not receive the raised event.

Similarly, debugger 1400 enables a developer to visualize state store1424 within a driver application. In some embodiments, debugger 1400enables the developer to review how state store 1424 interacts withmicro-applications 1434, 1436, 1438, and 1440. For example, debuggerenables the developer to visualize the logical flow of steps. At 1426micro-application 1434 detects an updated state belonging to a category.State change information is sent to state store 1424 for storage. Atstep 1428, a determination that micro-application 1436 is subscribed toreceive state change information relating to the category (oralternatively relating to micro-application 1434) causesmicro-application 1436 to receive the change information. At step 1430,a determination that micro-application 1438 is subscribed to receivestate change information relating to the category, but that thesubscription occurred late, causes micro-application 1438 to not receivethe state change information. At step 1432, a determination thatmicro-application 1440 is not subscribed to receive events belonging tothe category causes micro-application 1440 to not receive the statechange information.

FIG. 15 is a flowchart of an exemplary computer-implemented method 1500for providing a digital experience through an application in accordancewith some embodiments. Method 1500 may comprise step 1502 of detecting,at an event manager of a first micro-application, an application eventbelonging to a category. Method 1500 may comprise step 1504 ofdetecting, at a state manager of the first micro-application, anapplication state belonging to the category. Method 1500 may comprisestep 1506 of receiving, at an event hub, the detected application eventfrom the event manager of the first micro-application. Method 1500 maycomprise step 1508 of receiving, at a state store, the detectedapplication state from the state manager of the first micro-application.Method 1500 may comprise step 1510 of storing, at the state store, thedetected application state. Method 1500 may comprise step 1512 ofreceiving, at an event manager of a second micro-application, thedetected application event from the event hub. Method 1500 may comprisestep 1514 of receiving, at a state manager of the secondmicro-application, the detected application state from the state store.

The present disclosure has been presented for purposes of illustration.It is not exhaustive and is not limited to precise forms or embodimentsdisclosed. Modifications and adaptations of the embodiments will beapparent from consideration of the specification and practice of thedisclosed embodiments. For example, the described implementationsinclude hardware, but systems and methods consistent with the presentdisclosure can be implemented with hardware and software. In addition,while certain components have been described as being coupled to oneanother, such components may be integrated with one another ordistributed in any suitable fashion.

Moreover, while illustrative embodiments have been described herein, thescope includes any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations and/or alterations based on the presentdisclosure. The elements in the claims are to be interpreted broadlybased on the language employed in the claims and not limited to examplesdescribed in the present specification or during the prosecution of theapplication, which examples are to be construed as nonexclusive.Further, the steps of the disclosed methods can be modified in anymanner, including reordering steps and/or inserting or deleting steps.

The features and advantages of the disclosure are apparent from thedetailed specification, and thus, it is intended that the appendedclaims cover all systems and methods falling within the true spirit andscope of the disclosure. As used herein, the indefinite articles “a” and“an” mean “one or more.” Similarly, the use of a plural term does notnecessarily denote a plurality unless it is unambiguous in the givencontext. Words such as “and” or “or” mean “and/or” unless specificallydirected otherwise. Further, since numerous modifications and variationswill readily occur from studying the present disclosure, it is notdesired to limit the disclosure to the exact construction and operationillustrated and described, and accordingly, all suitable modificationsand equivalents may be resorted to, falling within the scope of thedisclosure.

Other embodiments will be apparent from consideration of thespecification and practice of the embodiments disclosed herein. It isintended that the specification and examples be considered as exampleonly, with a true scope and spirit of the disclosed embodiments beingindicated by the following claims.

According to some embodiments, the operations, techniques, and/orcomponents described herein can be implemented by a device or system,which can include one or more special-purpose computing devices. Thespecial-purpose computing devices can be hard-wired to perform theoperations, techniques, and/or components described herein, or caninclude digital electronic devices such as one or moreapplication-specific integrated circuits (ASICs) or field programmablegate arrays (FPGAs) that are persistently programmed to perform theoperations, techniques and/or components described herein, or caninclude one or more hardware processors programmed to perform suchfeatures of the present disclosure pursuant to program instructions infirmware, memory, other storage, or a combination. Such special-purposecomputing devices can also combine custom hard-wired logic, ASICs, orFPGAs with custom programming to accomplish the technique and otherfeatures of the present disclosure. The special-purpose computingdevices can be desktop computer systems, portable computer systems,handheld devices, networking devices, or any other device that canincorporate hard-wired and/or program logic to implement the techniquesand other features of the present disclosure.

The one or more special-purpose computing devices can be generallycontrolled and coordinated by operating system software, such as iOS,Android, Blackberry, Chrome OS, Windows XP, Windows Vista, Windows 7,Windows 8, Windows Server, Windows CE, Unix, Linux, SunOS, Solaris,VxWorks, or other compatible operating systems. In other embodiments,the computing device can be controlled by a proprietary operatingsystem. Operating systems can control and schedule computer processesfor execution, perform memory management, provide file system,networking, I/O services, and provide a user interface functionality,such as a graphical user interface (“GUI”), among other things.

Furthermore, although aspects of the disclosed embodiments are describedas being associated with data stored in memory and other tangiblecomputer-readable storage mediums, one skilled in the art willappreciate that these aspects can also be stored on and executed frommany types of tangible computer-readable media, such as secondarystorage devices, like hard disks, floppy disks, or CD-ROM, or otherforms of RAM or ROM. Accordingly, the disclosed embodiments are notlimited to the above described examples, but instead are defined by theappended claims in light of their full scope of equivalents.

Moreover, while illustrative embodiments have been described herein, thescope includes any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations or alterations based on the presentdisclosure. The elements in the claims are to be interpreted broadlybased on the language employed in the claims and not limited to examplesdescribed in the present specification or during the prosecution of theapplication, which examples are to be construed as non-exclusive.Further, the steps of the disclosed methods can be modified in anymanner, including by reordering steps or inserting or deleting steps.

It is intended, therefore, that the specification and examples beconsidered as example only, with a true scope and spirit being indicatedby the following claims and their full scope of equivalents.

What is claimed is:
 1. A computer-implemented driver applicationexecuted by a processor for managing a plurality of micro-applicationsto provide a digital experience, comprising: a first and a secondmicro-application, wherein the first micro-application comprises: afirst micro-application event manager configured to detect anapplication event belonging to a category; and a first micro-applicationstate manager configured to detect an application state belonging to thecategory; an event hub configured to receive the detected applicationevent from the first micro-application event manager of the firstmicro-application; a state store configured to store the detectedapplication state received from the first micro-application statemanager of the first micro-application; an event listener configured todetermine whether the application event belonging to the category isreceived at the event hub; and a router configured to route the detectedapplication event, based on the determination, from the event hub to thesecond micro-application; wherein the second micro-applicationcomprises: a second micro-application event manager configured toreceive the detected application event from the event hub, and a secondmicro-application state manager configured to receive the detectedapplication state from the state store.
 2. The driver application ofclaim 1, wherein the event hub is configured to receive the detectedapplication event in response to a user interaction with the firstmicro-application.
 3. The driver application of claim 1, comprising: anerror handler configured to detect an error condition in at least one ofthe first micro-application and the second micro-application.
 4. Thedriver application of claim 1, comprising: a page component configuredto position the first micro-application at a first position within apage and position the second micro-application at a second positionwithin the page.
 5. The driver application of claim 4, wherein: the pagecomponent is configured to display the first micro-application and thesecond micro-application using a common style scheme.
 6. The driverapplication of claim 4, wherein the first and second micro-applicationsare loaded onto the page component using a web platform.
 7. The driverapplication of claim 1, wherein the driver application comprises asingle page application.
 8. The driver application of claim 1,comprising: a common library configured to store a resource and afunction for at least one of the first and second micro-applications. 9.The driver application of claim 1, wherein each of the first and secondmicro-applications further comprise a front-end interface configured tointerface with a user.
 10. The driver application of claim 9, whereinthe front-end interface generates a user interaction data based on auser interaction with the first micro-application.
 11. The driverapplication of claim 10, wherein the event hub is configured to receivethe detected application event from the first micro-application based onthe user interaction data.
 12. The driver application of claim 1,wherein the driver application is configured to: load, in response tothe event listener determining that the event hub received theapplication event belonging to the category, a third micro-application.13. The driver application of claim 12, wherein the thirdmicro-application comprises a third micro-application state managerconfigured to receive the detected application state from the statestore.
 14. The driver application of claim 1, wherein the firstmicro-application comprises an outer interface configured to exchangeinformation with a source of information.
 15. The driver application ofclaim 1, wherein: the second micro-application is subscribed to receivethe application event belonging to the category; and the event listeneris configured to listen for the application event belonging to thecategory based on the subscription.
 16. The driver application of claim1, wherein: the second micro-application is subscribed to receive theapplication state belonging to the category; and the state store isconfigured to transmit the detected application state to the secondmicro-application state manager based on the subscription.
 17. Acomputer-implemented method for providing a digital experience using adriver application, the method comprising the following operationsperformed by at least one processor: detecting, at an event manager of afirst micro-application, an application event belonging to a category;detecting, at a state manager of the first micro-application, anapplication state belonging to the category; receiving, at an event hub,the detected application event from the event manager of the firstmicro-application; receiving, at a state store, the detected applicationstate from the state manager of the first micro-application; storing, atthe state store, the detected application state from the firstmicro-application state manager; determining, at an event listener,whether the application event belonging to the category is received atthe event hub; routing, via a router, the detected application eventfrom the event hub to a second micro-application based on thedetermination; receiving, at an event manager of the secondmicro-application, the detected application event from the event hub viathe router; and receiving, at a state manager of the secondmicro-application, the detected application state from the state store.18. The computer-implemented method of claim 17, further comprising thefollowing operations performed by the driver application: determiningwhether the second micro-application is subscribed to receive theapplication event belonging to the category; and transmitting, based onthe determination, the detected application event belonging to thecategory to the second micro-application event manager.
 19. Thecomputer-implemented method of claim 17, further comprising thefollowing operations performed by the driver application: determiningwhether the second micro-application is subscribed to receive theapplication state belonging to the category; and transmitting, based onthe determination, the detected application state to the secondmicro-application state manager.
 20. A tangible, non-transitorycomputer-readable memory device that stores a set of instructions that,when executed by at least one processor, cause the at least oneprocessor to perform operations comprising: detecting, at an eventmanager of a first micro-application, an application event belonging toa category; detecting, at a state manager of the firstmicro-application, an application state belonging to the category;receiving, at an event hub, the detected application event from theevent manager of the first micro-application; receiving, at a statestore, the detected application state from the state manager of thefirst micro-application; storing, at the state store, the detectedapplication state from the first micro-application state manager;determining, at an event listener, whether the application eventbelonging to the category is received at the event hub; routing, via arouter, the detected application event from the event hub to a secondmicro-application based on the determination; receiving, at an eventmanager of the second micro-application, the detected application eventfrom the event hub via the router; and receiving, at a state manager ofthe second micro-application, the detected application state from thestate store.